Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

2132

reference
66-tree-1
name
2132
tree-preservation-order

undefined

66-tpo-1
uprn
address-text
point
POINT (-0.940237 50.845710)
geometry
MULTIPOLYGON (((-0.940181 50.845704,-0.940183 50.845715,-0.940191 50.845725,-0.940203 50.845733,-0.940219 50.845738,-0.940237 50.845740,-0.940254 50.845739,-0.940270 50.845734,-0.940283 50.845726,-0.940291 50.845716,-0.940294 50.845705,-0.940292 50.845694,-0.940284 50.845683,-0.940271 50.845675,-0.940256 50.845670,-0.940238 50.845668,-0.940221 50.845670,-0.940205 50.845675,-0.940192 50.845683,-0.940184 50.845693,-0.940181 50.845704)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL